Method and apparatus for reducing power consumption based on use pattern of user

ABSTRACT

A device and method of managing power are provided. The device includes a user input unit configured to receive a user input from a user, an output unit configured to output information based on the user input, and a controller configured to, when the user input is not received, determine whether or not an out-focus status in which the user does not use the device has started, determine, when it is determined that the out-focus status has started, a period in which the out-focus status is to be maintained based on information about a probability of the out-focus status according to a context of the device, and stop, when the period in which the out-focus status is to be maintained is equal to or greater than a reference time period, an application executed in the device.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application claims the benefit under 35 U.S.C. § 119(a) of a Koreanpatent application filed on Feb. 13, 2015 in the Korean IntellectualProperty Office and assigned Serial number 10-2015-0022718, the entiredisclosure of which is hereby incorporated by reference.

TECHNICAL FIELD

The present disclosure relates to methods and apparatuses for improvingefficiency of power consumption of a battery of a device, based on a usepattern of a user with respect to the device.

BACKGROUND

Currently, functions of a device have become increasingly complex anddiverse and thus, power consumption of the device is increased, whereasa size of the device is reduced. Also, the number of portable deviceshas increased, whereas a size of a battery in each device is decreased.Therefore, there is an increasing demand for improving efficiency ofpower consumption of a battery of a device.

In order to reduce power consumption of a battery, a low-power hardwarechipset may be used or an operating voltage of a device may bedecreased. Also, hardware of the device may be integrated in the form ofa system on chip (SoC). However, since these physical attempts havelimitations in reducing the power consumption, it is required to reducethe power consumption by intelligently controlling operations of thedevice by using a difference between a use pattern of the device of auser and a use pattern of another device of another user.

The above information is presented as background information only, toassist with an understanding of the present disclosure. No determinationhas been made, and no assertion is made, as to whether any of the abovemight be applicable as prior art with regard to the present disclosure.

SUMMARY

Aspects of the present disclosure are provided to address at least theabove-mentioned problems and/or disadvantages, and provide at least theadvantages described below. Accordingly, an aspect of the presentdisclosure is to provide methods and apparatuses for improvingefficiency of power consumption of a battery of a device, based on a usepattern of a user with respect to the device.

In accordance with an aspect of the present disclosure, a device isprovided. The device includes a user input unit configured to receive auser input from a user, an output unit configured to output informationbased on the user input, and a controller configured to determine, whenthe user input is not received, whether or not an out-focus status inwhich the user does not use the device has started, determine, when itis determined that the out-focus status has started, a period in whichthe out-focus status is to be maintained based on information about aprobability of the out-focus status according to a context of thedevice, and stop, when the period in which the out-focus status is to bemaintained is equal to or greater than a reference time period, anapplication executed in the device.

In accordance with another aspect of the present disclosure, a method ofmanaging power is provided. The method of managing power includesdetermining, when a user input is not received from a user, whether ornot an out-focus status in which the user does not use a device hasstarted, determining, when it is determined that the out-focus statushas started, a period in which the out-focus status is to be maintainedbased on information about a probability of the out-focus statusaccording to a context of the device, and stopping, when the period inwhich the out-focus status is to be maintained is equal to or greaterthan a reference time period, an operation of an application executed inthe device.

Other aspects, advantages, and salient features of the disclosure willbecome apparent to those skilled in the art from the following detaileddescription, which, taken in conjunction with the annexed drawings,discloses various embodiments of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, features, and advantages of certainembodiments of the present disclosure will be more apparent from thefollowing description taken in conjunction with the accompanyingdrawings, in which:

FIG. 1 is a diagram illustrating a method of efficiently controllingpower consumption of a battery of a device, based on a period in whichan out-focus status of the device is to be maintained, according to anembodiment of the present disclosure;

FIG. 2 is a flowchart illustrating a method of controlling an operationof an application based on an out-focus probability, according to anembodiment of the present disclosure;

FIG. 3 is a flowchart illustrating a method of resuming a stoppedoperation of an application, based on an end of an out-focus status,according to an embodiment of the present disclosure;

FIGS. 4A and 4B illustrate diagrams in relation to a method ofdetermining that an out-focus status has started, according to variousembodiments of the present disclosure;

FIG. 5 illustrates a table related to a method of determining an end ofan out-focus status, according to an embodiment of the presentdisclosure;

FIG. 6 is a flowchart illustrating a method of determining an out-focusprobability based on device use pattern information of a user, accordingto an embodiment of the present disclosure;

FIG. 7 illustrates device use pattern information of a user according toan embodiment of the present disclosure;

FIG. 8 illustrates a device in relation to a method of displaying anout-focus status according to a context of the device, according to anembodiment of the present disclosure;

FIG. 9 illustrates a graph related to a method of determining out-focusprobabilities according to time, according to an embodiment of thepresent disclosure;

FIG. 10A illustrates a graph related to a method of determining anout-focus probability according to a location, according to anembodiment of the present disclosure;

FIG. 10B illustrates a graph related to a method of determining anout-focus probability according to a transportation type, according toan embodiment of the present disclosure;

FIGS. 11A to 11D illustrate graphs related to a method of calculating anout-focus probability according to a status of a device or a surroundingenvironment of the device, according to various embodiments of thepresent disclosure;

FIGS. 12A and 12B illustrate diagrams related to a method of calculatingan order of execution probabilities of applications according to acontext, according to various embodiments of the present disclosure;

FIG. 13 is a flowchart illustrating a method of determining a period inwhich an out-focus status is to be maintained based on out-focusprobabilities according to time, according to an embodiment of thepresent disclosure;

FIG. 14 is a flowchart illustrating a method of determining reliabilityof a period in which an out-focus status is to be maintained based on anout-focus probability according to a context, according to an embodimentof the present disclosure;

FIG. 15 illustrates a diagram related to a method of determining aperiod in which an out-focus status is to be maintained based onout-focus probabilities according to time, according to an embodiment ofthe present disclosure;

FIG. 16A illustrates a diagram related to a method of adjustingreliability by considering an out-focus probability at a location wherean out-focus status has started according to an embodiment of thepresent disclosure;

FIG. 16B illustrates a diagram related to a method of adjustingreliability by considering an out-focus probability corresponding to astatus of the device when an out-focus status has started according toan embodiment of the present disclosure;

FIG. 17A is a flowchart illustrating a method of re-determiningreliability of a period in which an out-focus status is to be maintainedsince a status value of a context of the device is changed, according toan embodiment of the present disclosure;

FIGS. 17B and 17C illustrate diagrams related to a method ofre-determining reliability of a period in which an out-focus status isto be maintained since a status value of a context of the device ischanged, according to various embodiments of the present disclosure;

FIG. 18 is a flowchart illustrating a method of stopping an operation ofan application executed in the device based on a period in which anout-focus status is to be maintained and reliability of the period,according to an embodiment of the present disclosure;

FIG. 19 illustrates a table related to a method of controlling anoperation of a background application, according to an embodiment of thepresent disclosure;

FIG. 20 illustrates a table related to a method of stopping an operationof an application according to reliability of a period in which anout-focus status is to be maintained, according to an embodiment of thepresent disclosure;

FIG. 21 illustrates a graph related to a method of controlling dataexchange of an application based on out-focus probabilities according totime, according to an embodiment of the present disclosure;

FIGS. 22A and 22B illustrate diagrams related to a method of controllingan event when the event occurs during an out-focus status period,according to various embodiments of the present disclosure;

FIG. 23 illustrates a device in relation to a method of displayingidentification information of an application based on an executionprobability of the application according to a context of the device,according to an embodiment of the present disclosure;

FIGS. 24A and 24B illustrate a device in relation to a method ofproviding a user interface for controlling an operation of anapplication based on a use pattern of a user, according to variousembodiments of the present disclosure;

FIG. 25 is a block diagram illustrating a device according to anembodiment of the present disclosure; and

FIG. 26 is a block diagram illustrating a device according to anembodiment of the present disclosure.

Throughout the drawings, like reference numerals will be understood torefer to like parts, components, and structures.

DETAILED DESCRIPTION

The following description with reference to the accompanying drawings isprovided to assist in a comprehensive understanding of variousembodiments of the present disclosure as defined by the claims and theirequivalents. It includes various specific details to assist in thatunderstanding but these are to be regarded as merely exemplary.Accordingly, those of ordinary skill in the art will recognize thatvarious changes and modifications of the various embodiments describedherein can be made without departing from the scope and spirit of thepresent disclosure. In addition, descriptions of well-known functionsand constructions are omitted for clarity and conciseness.

The terms and words used in the following description and claims are notlimited to the bibliographical meanings, but, are merely used by theinventor to enable a clear and consistent understanding of the presentdisclosure. Accordingly, it should be apparent to those skilled in theart that the following description of various embodiments of the presentdisclosure is provided for illustration purpose only and not for thepurpose of limiting the present disclosure as defined by the appendedclaims and their equivalents.

It is to be understood that the singular forms “a”, “an”, and “the”,include plural referents unless the context clearly dictates otherwise.Thus, for example, reference to “a component surface” includes referenceto one or more of such surfaces.

Also, when a part “includes” or “comprises” an element, unless there isa particular description contrary thereto, the part can further includeother elements, not excluding the other elements. In the followingdescription, terms such as “unit” and “module” indicate a unit forprocessing at least one function or operation, wherein the unit and theblock may be embodied as hardware or software or embodied by combininghardware and software.

Throughout the specification, the term “out-focus status” may mean astatus in which a user does not use a device. For example, the out-focusstatus may indicate a status in which the device does not outputinformation, according to non-reception of a user input. Also, theout-focus status may indicate a status in which, even if the deviceoutputs information, the user does not receive the output information.In an embodiment, the term “out-focus status” may be referred to as“non-use status” or “out-of-coverage status”.

Throughout the specification, the term “context of a device” maycorrespond to information indicating a status of the device. Forexample, the context of the device may include, but is not limited to, atime, a location of the device, a status of the device, and asurrounding environment of the device.

One or more embodiments will now be described more fully with referenceto the accompanying drawings. However, the one or more embodiments maybe embodied in many different forms, and should not be construed asbeing limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure will be thorough andcomplete, and will fully convey the concept of the one or moreembodiments to those of ordinary skill in the art.

As used herein, the term “and/or” includes any and all combinations ofone or more of the associated listed items. Expressions such as “atleast one of,” when preceding a list of elements, modify the entire listof elements and do not modify the individual elements of the list.

FIG. 1 is a diagram illustrating a method of efficiently controllingpower consumption of a battery of a device based on a period in which anout-focus status of the device is to be maintained, according to anembodiment of the present disclosure.

FIG. 26 illustrates a block diagram of a device according to anembodiment of the present disclosure.

Referring to FIGS. 1 and 26, a device 100 may calculate a probability ofa user having an out-focus status with respect to the device 100, andmay improve efficiency of power consumption of a battery 180 of thedevice 100 based on the calculated probability with respect to theout-focus status.

The out-focus status may mean a status in which the user does not usethe device 100. Also, throughout the specification, a probability of theout-focus status may be referred to as an out-focus probability.

The device 100 may determine a start or end of the out-focus status. Forexample, when a user input is not received and thus a screen of thedevice 100 is turned off, the device 100 may determine that theout-focus status has started. As another example, when a strength of ashort-distance wireless signal between the device 100 and a wearabledevice becomes equal to or less than a reference strength, the device100 may determine that the out-focus status has started.

When the device 100 determines that the out-focus status has beenstarted, the device 100 may determine a period in which the out-focusstatus is to be maintained and reliability of the period, based on anout-focus probability according to a context of the device 100. Thecontext of the device 100 may include, but is not limited to, a time, alocation of the device 100, a status of the device 100, and asurrounding environment of the device 100.

The out-focus probability according to the context of the device 100 maybe previously calculated by the device 100. For example, based on deviceuse pattern information of the user during a preset time period, thedevice 100 may calculate the out-focus probability according to thetime, a place of the device 100, a status of the device 100, or asurrounding environment of the device 100.

When the context of the device 100 is changed, the device 100 maydetermine a period in which an out-focus status is to be maintained andreliability of the period, based on an out-focus probabilitycorresponding to a changed context.

Based on the period in which the out-focus status is to be maintainedand the reliability of the period in which the out-focus status is to bemaintained, the device 100 may stop an operation of an executedapplication and thus may improve efficiency of the power consumption.

For example, in a case where the period in which the out-focus status isto be maintained is equal to or greater than a reference time and thereliability is equal to or greater than a reference value, the device100 may stop data exchange between an external server and a backgroundprocessor of the device 100 and thus may reduce the power consumption ofthe battery. As another example, the device 100 may block an update ofan application and thus may reduce the power consumption of the battery.As another example, even if the device 100 receives push data from anexternal server, the device 100 may not notify the user and thus mayreduce the power consumption of the battery.

As another example, the device 100 may recommend the user for anapplication having a high execution number of times, based on anexecution number of times of applications according to the context ofthe device 100. Accordingly, the device 100 may decrease a user's touchinput to execute an application and thus may reduce the powerconsumption of the battery.

FIG. 2 is a flowchart illustrating a method of controlling an operationof an application based on an out-focus probability, the method beingperformed by a device, according to an embodiment of the presentdisclosure.

Referring to FIG. 2, in operation S210, when a user input is notreceived from a user, a device 100 may determine whether an out-focusstatus in which the user does not use the device 100 has started.

When the user input is not received from the user for a preset timeperiod, the device 100 may inactivate a display unit (not shown) of thedevice 100. When the display unit of the device 100 is inactivated,i.e., when a screen of the device 100 is turned off, the device 100 maydetermine that the out-focus status has started. In an embodiment, whenan operation mode of the device 100 is changed to a sleep mode or apower saving mode, the device 100 may determine that the out-focusstatus has started.

While an image or sound to notify the user about reception of a callconnection request is output, if a user input for call connection is notreceived, the device 100 may determine that the out-focus status hasstarted.

After an image or sound to notify the user about reception of a messageis output, if a user input for checking the message is not receivedwithin a preset time period, the device 100 may determine that theout-focus status has started.

While the device 100 communicates with a wearable device, if a strengthof a short-distance wireless signal between the device 100 and thewearable device becomes equal to or less than a reference strength, thedevice 100 may determine that the out-focus status has started.

In operation S220, since the device 100 determined that the out-focusstatus started, the device 100 may determine a period in which theout-focus status is to be maintained based on information about aprobability of the out-focus status according to a context of the device100.

The context of the device 100 may include, but is not limited to, atime, a location of the device 100, a status of the device 100, and asurrounding environment of the device 100.

For example, based on an out-focus probability according to the time,the device 100 may calculate the period in which the out-focus status isto be maintained from a start of the out-focus status.

In operation S230, when the calculated period in which the out-focusstatus is to be maintained is equal to or greater than a reference timeperiod, the device 100 may stop an operation of an application that isexecuted in the device 100.

Based on the out-focus probability of the period in which the out-focusstatus is to be maintained from the start of the out-focus status, thedevice 100 may determine reliability of the period in which theout-focus status is to be maintained. Only when the determinedreliability of the period in which the out-focus status is to bemaintained is equal to or greater than a reference, the device 100 maystop the operation of the application that is executed in the device100.

In this case, the device 100 may further consider an out-focusprobability with respect to a location of the device 100 at the start ofthe out-focus status, and may determine the reliability of the period inwhich the out-focus status is to be maintained.

In this case, the device 100 may further consider an out-focusprobability with respect to a status of the device 100 at the start ofthe out-focus status, and may determine the reliability of the period inwhich the out-focus status is to be maintained.

When the period in which the out-focus status is to be maintained isequal to or greater than a reference time period, the device 100 maystop data exchange between a server and a background application of thedevice 100 and thus may improve efficiency of power consumption of abattery of the device 100.

When the period in which the out-focus status is to be maintained isequal to or greater than the reference time period, even if an eventoccurs in the device 100, the device 100 may not output information ofthe event and thus may improve the efficiency of the power consumption.

When the period in which the out-focus status is to be maintained isequal to or greater than the reference time period, the device 100 maynot receive updated data from the server and thus may improve theefficiency of the power consumption.

Based on information about an application use pattern of the user, thedevice 100 may adjust a position, a shape, a size, or a color of an iconof an application according to a context of the device 100, and thus mayallow an application which is frequently used according to the contextof the device 100, to be more easily found than an application that isnot frequently used. Accordingly, an image conversion required to selectan application is decreased, so that the efficiency of the powerconsumption of the battery of the device 100 may be improved.

FIG. 3 is a flowchart illustrating a method of resuming a stoppedoperation of an application based on an end of an out-focus status, themethod being performed by a device, according to an embodiment of thepresent disclosure.

Referring to FIG. 3, in operation S310, after the operation of theapplication is stopped, a device 100 may receive a user input from auser.

For example, the device 100 may inactivate a screen in the out-focusstatus, and while the screen is inactivated, the device 100 may receivea user input for pressing a key to activate the screen.

In operation S320, when the user input is received, the device 100 mayresume the stopped operation of the application.

When the user input is received in the out-focus status, the device 100may cancel the out-focus status and may resume the stopped operation ofthe application.

For example, the device 100 may resume a stopped data exchange between aserver and a background application of the device 100. The device 100may output event information that was not output. The device 100 mayreceive, from the server, updated data that was not received, and mayupdate an application by using the updated data.

FIG. 4A illustrates a table related to a method of determining that anout-focus status has started, the method being performed by a device,according to an embodiment of the present disclosure.

Referring to FIG. 4A, the device 100 may determine the out-focus statusbased on a predefined operation of a device 100 and a user's reactionwith respect to the predefined operation of the device 100.

For example, when the device 100 receives a user input for turning off ascreen when the screen of the device 100 is turned on, the device 100may turn off the screen. When the device 100 does not receive a userinput for a preset time period, the device 100 may turn off the screen.Since the screen is turned off, the device 100 may determine that theout-focus status has started.

In an embodiment, when an operation mode of the device 100 is changed toa sleep mode, the device 100 may determine that the out-focus status hasstarted. The sleep mode may indicate a mode during which operations ofthe device 100 are temporally stopped. For example, during the sleepmode, the device 100 may store in a random-access memory (RAM), amachine state (e.g., a register value, a stack pointer value, etc.)indicating an operating status of the device 100, may supply to the RAMpower sufficient only to retain data in the RAM, and may block a powersupply to other physical configurations of the device 100, thustemporally stopping operation of the device 100. In some embodiments,the sleep mode may be referred to as a power saving mode. When thedevice 100 receives the user input for turning off the screen or doesnot receive the user input for the preset time period, the device 100may change the operation mode of the device 100 to the sleep mode.

As another example, when the device 100 receives a call connectionrequest from a telephone network server, the device 100 may output animage or sound to notify the user about reception of the call connectionrequest. In this regard, when a user input for call connection is notreceived and thus the call connection request is refused, the device 100may determine that the out-focus status has started.

For example, when a push message is received from a server, the device100 may output an image or sound to notify the user about reception ofthe push message. When a user input for checking the push message is notreceived, the device 100 may determine that the out-focus status hasstarted.

As another example, when the user wears a wearable device such as awatch and uses both the device 100 and the watch, the device 100 maycommunicate with the wearable device via short-distance communication.

FIG. 4B illustrates a diagram in relation to a method of determiningthat an out-focus status has started, the method being performed by adevice, according to an embodiment of the present disclosure.

Referring to FIG. 4B, when a user becomes distant from a device 100, astrength (e.g., a received signal strength indicator (RSSI)) of ashort-distance wireless signal between the device 100 and a wearabledevice 410 may be decreased. When the strength of the short-distancewireless signal between the device 100 and the wearable device 410becomes equal to or less than a reference strength, the device 100 maydetermine that the out-focus status has started. In a case where theuser becomes distant from the device 100 and thus Bluetooth pairingbetween the device 100 and the wearable device 410 is discontinued, thedevice 100 may determine that the out-focus status has started.

When the screen is turned off, a call is missed, or a message is missed,the device 100 may determine the out-focus status by further consideringa type of an application executed in the device 100.

When the screen is turned off, the call is missed, or the message ismissed, if an application for outputting data such as music or a movingpicture is executed in the device 100, the device 100 may not determinethat the out-focus status has started but may determine that an in-focusstatus in which the user uses the device 100 is maintained. When anapplication for exchanging data between an external device and thedevice 100 is executed, wherein the exchange, e.g., tethering or dataexchange with a personal computer (PC), is performed due to manipulationby the user, the device 100 may determine that the in-focus status ismaintained.

FIG. 5 illustrates a table related to a method of determining an end ofan out-focus status, the method being performed by a device, accordingto an embodiment of the present disclosure.

Referring to FIG. 5, when a device 100 receives a user input by using asensor in the device 100, the device 100 may determine that theout-focus status has been ended. The sensor in the device 100 mayinclude, but is not limited to, a button key, a touch key, an operationsensor, a posture sensor, a motion sensor, or the like.

In an embodiment, even if the device 100 receives a first input by usingthe sensor in the device 100, if a second input is not received for apreset time period from when the first input is received, the device 100may not determine that the out-focus status has been ended but maydetermine that the out-focus status is maintained. Accordingly, even ifthe button key or the touch key is pressed regardless of a user'sintention since the device 100 is inside a pocket or a bag, the device100 may not determine that the out-focus status has been ended but maydetermine that the out-focus status is maintained.

In a case where an application is executed in the device 100 and thusinformation is output, if a strength of a short-distance wireless signalbetween the device 100 and a wearable device is decreased and then isincreased, the device 100 may determine that the out-focus status hasstarted and then is ended again.

FIG. 6 is a flowchart illustrating a method of determining an out-focusprobability based on device use pattern information of a user, themethod being performed by a device, according to an embodiment of thepresent disclosure.

Referring to FIG. 6, in operation S610, a device 100 may store thedevice use pattern information of the user.

FIG. 7 illustrates device use pattern information of a user according toan embodiment of the present disclosure.

Referring to FIG. 7, the device use pattern information may include alocation of the device 100 according to time, a status of the device100, and an environment surrounding the location of the device 100.Also, the device use pattern information may include one or more piecesof identification information of applications and entry paths of theapplications that are executed according to time. The device use patterninformation may include information about a user's reaction with respectto an event output from the device 100.

The device 100 may store locations of the device 100 according to time.For example, the device 100 may periodically obtain location informationof the device 100 by using a global positioning system (GPS) sensor inthe device 100. The device 100 may store the obtained locationinformation in correspondence to a time when the location information isobtained.

The device 100 may store one or more pieces of information about thestatus of the device 100 according to time. The information about thestatus of the device 100 may include, but is not limited to, informationabout whether or not earphones are connected, information about a typeof a wearable device connected to the device 100, information about atype of a wireless network connected to the device 100, informationabout an Internet protocol (IP) address of an access point that connectsthe device 100 and the wireless network, information aboutminute-by-minute power consumption of a battery of the device 100, andinformation about whether or not the battery of the device 100 is beingcharged. When the status of the device 100 is changed, the device 100may store a changed status corresponding to a time of the changedstatus.

The device 100 may store a time-based change of the environment thatsurrounds the location of the device 100. For example, the device 100may obtain an illuminance level or a noise level around the device 100by using an illuminance sensor or a noise sensor in the device 100.Since the device 100 obtains information about a change of theenvironment, the device 100 may store the obtained information about thechange in correspondence to a time when the information is obtained.

The device 100 may store execution information of an application. Forexample, when execution of the application is started or is ended, thedevice 100 may store whether or not the application is started or isended corresponding to a start time or an end time.

The device 100 may store a user's reaction with respect to a messagereception notice or a call connection request notice.

In an embodiment, the device 100 may determine whether an out-focusstatus has started or has been ended, and may store the out-focus statuscorresponding to every start time or every end time of the out-focusstatus.

In operation S620, the device 100 may calculate, based on the device usepattern information of the user, an out-focus probability and anapplication execution probability according to a context of the device100.

The device 100 may obtain pre-stored out-focus status informationaccording to time. Also, the device 100 may determine a status in whichan application is not executed, as an out-focus status in which the userdoes not use the device 100, and thus may obtain out-focus statusinformation by referring to a pre-stored execution time of theapplication.

The device 100 may calculate the out-focus probability based on one ormore pieces of out-focus status information during a preset period.

For example, the device 100 may determine the out-focus probability inreference time units between 0 a.m. through 24 p.m., based on one ormore pieces of out-focus status information during recent days. Thereference time units may be, but is not limited to, 5 minutes, 10minutes, 30 minutes, or 1 hour units.

The device 100 may determine out-focus probabilities corresponding todays of the week, respectively. The device 100 may determine anout-focus probability corresponding to weekdays or weekends.

The device 100 may determine an out-focus probability according to alocation. For example, the device 100 may obtain a value calculated byadding a value of an out-focus status according to the location to avalue of a time period of the out-focus status at the same locationduring a preset period. The device 100 may divide the obtained value bya time period during which the device 100 is located at the samelocation during the preset period, and thus may determine the out-focusprobability at the same location.

The device 100 may determine an out-focus probability according to atransportation type. For example, the device 100 may obtain a valuecalculated by adding a value of an out-focus status according to thetransportation type to a value of a time period of the out-focus statusin the same transportation type during a preset period. The device 100may divide the obtained value by a time period during which the device100 is located in the same transportation type during the preset period,and thus may determine the out-focus probability in the sametransportation type.

Also, the device 100 may determine an out-focus probability according toa change in a status of the device 100. For example, the device 100 maydetermine an out-focus probability with respect to a wearable devicebased on a value of an out-focus status according to the wearable deviceconnected to the device 100.

The device 100 may determine an out-focus probability according to achange in an environment around the device 100. For example, the device100 may determine an out-focus probability according to a noise levelbased on a value of the out-focus probability according to the noiselevel.

The device 100 may autonomously calculate an out-focus probability ormay transmit to a pattern calculation server, information about a time,a location, a status of the device 100, and an environment surroundingthe location of the device 100, and may receive the out-focusprobability from the pattern calculation server. In this case, based onuse pattern information of the user which is received from the device100, the pattern calculation server may calculate the out-focusprobability according to a change in the environment surrounding thelocation of the device 100.

The device 100 may calculate an execution probability of each ofapplications according to a context of the device 100. The context mayinclude, but is not limited to, a time, a location of the device 100, astatus of the device 100, and a surrounding environment of the device100.

For example, the device 100 may divide total time periods in which a webbrowser is executed in the subway during a preset period by total timeperiods in which all applications are executed in the subway during thepreset period, and thus may calculate an execution probability of theweb browser with respect to the subway.

As another example, the device 100 may divide the number of times a gameapplication is executed when a type of network connected to the device100 is Wi-Fi by the number of times all applications are executed whenthe type of network connected to the device 100 is Wi-Fi, and thus maycalculate an execution probability of the game application with respectto Wi-Fi.

The device 100 may calculate a user's reaction probability with respectto an event based on the context. The device 100 may consider thecalculated user's reaction probability with respect to the event basedon the context and may calculate an out-focus probability with respectto the context.

For example, when the number of times a call is missed or a message isnot checked during an out-focus status in a particular time zone isgreater than in other time zones, the device 100 may set an out-focusprobability in the particular time zone to be higher than out-focusprobabilities in other time zones.

The device 100 may determine, based on calculated executionprobabilities of applications according to the context, an order of anexecution probability of an application among the applications accordingto the context.

The device 100 may calculate hourly power consumption of the battery 180with respect to a particular application. The device 100 may calculatehourly power consumption of the battery with respect to the context.

Referring again to FIG. 7, the device 100 may store use patterninformation of the user.

The device 100 may calculate latitudes and longitudes of the device 100which are changed according to movement of the device 100. In this case,the device 100 may also store times where the latitudes and longitudesare obtained.

In an embodiment, the device 100 may store an IP address of an accesspoint that connects the device 100 to a network. The device 100 mayrecognize a place, based on the stored IP address, and may store anout-focus status according to the identified place.

The device 100 may store information about a status of the device 100according to time. The status of the device 100 may include, but is notlimited to, connection or disconnection of earphones, a type of awearable device connected to the device 100, a network allowingcommunication between the device 100 and an external device, or powerconsumption of a battery of the device 100.

When the device 100 and the wearable device are connected to each other,the device 100 may receive identification information of the wearabledevice from the wearable device. The device 100 may determine the typeof the wearable device based on the received identification informationof the wearable device.

Whenever a preset status of the device 100 is changed, the device 100may store a time and the changed status. For example, when earphones areconnected or are disconnected, when the wearable device is connected oris disconnected, when the network connected to the device 100 ischanged, or when the power consumption of the battery is changedexceeding a reference range, the device 100 may store the changed statusand the time of the change.

The device 100 may store information about a surrounding environment ofthe device 100 according to time. The surrounding environment of thedevice 100 may include, but is not limited to, illuminance or noise.

The device 100 may store application execution information according totime. The application execution information may include, but is notlimited to, identification information of an application that isexecuted or is ended, time information about when the application isexecuted or is ended, and information about an entry path when theapplication is executed.

The device 100 may store information of a user's reaction with respectto an event. The event may include, but is not limited to, a messagereception notice, a call connection request notice, an alarm notice, aschedule notice, or the like.

In an embodiment, the device 100 may determine whether an out-focusstatus has started or has been ended, and whenever the out-focus statusstarts or is ended, the device 100 may store a start or an end of theout-focus status in correspondence to time.

FIG. 8 illustrates a device in relation to a method of displaying anout-focus status according to a context of the device, the method beingperformed by a device, according to an embodiment of the presentdisclosure.

Referring to FIG. 8, a device 100 may provide an out-focus statusaccording to time.

For example, when the device 100 receives a user input for selecting amenu to display an out-focus status, the device 100 may display an image810 indicating the out-focus status according to time.

The out-focus status according to time may include, but is not limitedto, an out-focus status detected on a particular date, an averageout-focus status of a particular day, an average out-focus status duringa particular period, an average out-focus status during weekdays, or anaverage out-focus status during a weekend.

FIG. 9 illustrates a graph related to a method of determining out-focusprobabilities according to time, the method being performed by a device,according to an embodiment of the present disclosure.

Referring to FIG. 9, a device 100 may calculate out-focus probabilitiesaccording to time between 0 a.m. through 24 p.m. on each of Mondaythrough Sunday.

For example, the device 100 may determine an out-focus probability inreference time units between 0 a.m. through 24 p.m., based oninformation about an out-focus status on recent Mondays.

For example, the device 100 may divide total time periods of out-focusstatuses between 22:00 to 22:10 for 30 Mondays by 300 minutes (e.g., 10minutes×30) that is a total time, and thus may determine an out-focusprobability between 22:00 to 22:10 on Monday.

The device 100 may calculate the out-focus probabilities according totime on each of Monday through Sunday or may calculate an out-focusprobability during weekdays or weekends.

FIG. 10A illustrates a graph related to a method of determining anout-focus probability according to a location, the method beingperformed by a device, according to an embodiment of the presentdisclosure.

Referring to FIG. 10A, a device 100 may calculate an out-focusprobability in a particular location or a particular movement path.

The device 100 may determine a place where the device 100 is located fora certain period of time, based on location information according totime with respect to the device 100. For example, the device 100 maydetermine a staying time period of the device 100 in each place, andwhen an average value of a staying time period of the device 100 in aparticular place is equal to or greater than a reference time period,the device 100 may determine the particular place as a place where thedevice 100 is mainly located. Accordingly, the device 100 may recognizea location such as a user's residence, workplace, or class room. Forexample, the device 100 may recognize a place where the device 100 islocated, based on an IP address of an access point that connects thedevice 100 to a network.

The device 100 may recognize a movement path where the device 100 ismainly moved based on location information according to time withrespect to the device 100. For example, the device 100 may determine amovement path where the device 100 is moved based on the locationinformation according to time, and when the number of using thedetermined movement path is equal to or greater than a reference number,the device 100 may determine the determined movement path as a pathwhere the device 100 is mainly moved. In this case, even if the path isone connected movement path, the device 100 may determine the path asdifferent movement paths according to movement speeds.

After the place where the device 100 is mainly located and the mainmovement paths of the device 100 are determined, the device 100 maycalculate an out-focus probability in a particular location and aparticular movement path.

For example, the device 100 may divide a total time period of anout-focus status in the particular location by a total staying timeperiod with respect to the particular location, and thus may calculatethe out-focus probability in the particular location. The device 100 maydivide a total time period of an out-focus status in the particularmovement path by a total staying time period with respect to theparticular movement path, and thus may calculate the out-focusprobability in the particular movement path.

FIG. 10B illustrates a graph related to a method of determining anout-focus probability according to a transportation type, the methodbeing performed by a device, according to an embodiment of the presentdisclosure.

Referring to FIG. 10B, a device 100 may calculate the out-focusprobability according to the transportation type.

For example, the device 100 may recognize the transportation type basedon location information according to time. For example, when thelocation information according to time with respect to the device 100 issimilar to a pre-stored movement path via the subway, the device 100 maydetermine that a user having the device 100 moved via the subway. Whenthe location information according to time with respect to the device100 is similar to a pre-stored movement pattern via a bus, the device100 may determine that the user having the device 100 moved via the bus.The movement pattern via the bus may be a pattern of stopping forseveral seconds at each of predefined bus stops.

When the location information according to time with respect to thedevice 100 indicates a pre-stored pattern of moving along a road, thedevice 100 may determine that the user having the device 100 moved via avehicle.

When the transportation type that is mainly used is determined, thedevice 100 may calculate the out-focus probability with respect to aparticular transportation type.

For example, the device 100 may divide a total time period of anout-focus status with respect to the particular transportation type by atotal time period of using the particular transportation type, and thusmay calculate the out-focus probability with respect to the particulartransportation type.

FIGS. 11A to 11D illustrate graphs related to a method of calculating anout-focus probability according to a status of a device or a surroundingenvironment of the device, the method being performed by a device,according to various embodiments of the present disclosure.

Referring to FIG. 11A, a device 100 may calculate an out-focusprobability about when a battery of the device 100 is being charged oris not charged based on information about an out-focus status withrespect to whether or not the battery is charged.

Referring to FIG. 11B, a device 100 may calculate an out-focusprobability with respect to an entry path of an application based oninformation about an out-focus status according to the entry path. Forexample, the entry path may include an entry path through an eventnotice or a direct entry path by a user.

Referring to FIG. 11C, a device 100 may calculate an out-focusprobability with respect to a type of a network based on informationabout an out-focus status according to the type of the network.

Referring to FIG. 11D, a device 100 may calculate an out-focusprobability with respect to a type or identification information of awearable device connected to the device 100 based on information aboutan out-focus status according to the type or identification informationof the wearable device.

FIGS. 12A and 12B illustrate diagrams related to a method of calculatingan order of execution probabilities of applications according to acontext, the method being performed by a device, according to variousembodiments of the present disclosure.

Referring to FIG. 12A, a device 100 may calculate the order of theexecution probabilities of the applications according to time based ondevice use pattern information of a user.

For example, the device 100 may divide a total time period in which aweb browser is executed from 18 p.m. through 18:30 p.m. during a presetperiod by a total time period in which all applications are executedduring the same time, and thus may calculate an execution probability ofthe web browser from 18 p.m. through 18:30 p.m.

When the execution probabilities of the applications installed in thedevice 100 are calculated, the device 100 may calculate an order of anapplication to be executed during a particular time based on thecalculated execution probabilities of the applications with respect tothe particular time.

Referring to FIG. 12B, the device 100 may calculate an order ofapplication execution probabilities according to a place, based on thedevice use pattern information of the user.

For example, the device 100 may divide a total time period in which agame application is executed in home during a preset period by a totaltime period in which all applications are executed in home during thepreset period, and thus may calculate a possibility of execution of thegame application in home.

When the execution probabilities of the applications installed in thedevice 100 are calculated, the device 100 may calculate the order of theapplication to be executed at the particular place based on thecalculated execution probabilities of the applications with respect tothe particular place.

FIG. 13 is a flowchart illustrating a method of determining a period inwhich an out-focus status is to be maintained based on out-focusprobabilities according to time, the method being performed by a device,according to an embodiment of the present disclosure.

Referring to FIG. 13, in operation S1310, a device 100 may determine,based on the out-focus probabilities according to time, whether or notan out-focus probability when an out-focus status starts is equal to orgreater than a threshold value.

For example, the threshold value may be 75% but is not limited thereto.

In operation S1320, if the out-focus probability when the out-focusstatus starts is equal to or greater than the threshold value, thedevice 100 may detect a point of time when the out-focus probabilitybecomes less than the threshold value after the out-focus status starts.

If the out-focus probability when the out-focus status starts is equalto or greater than the threshold value, the device 100 may detect apoint of time when the out-focus probability initially becomes less thanthe threshold value after the out-focus status starts.

In operation S1330, the device 100 may determine a period from when theout-focus status starts to when the out-focus probability becomes lessthan the threshold value as the period in which the out-focus status isto be maintained.

In an embodiment, if the out-focus probability when the out-focus statusstarts is equal to or greater than the threshold value, the device 100may detect a particular point of time when an average value of out-focusprobabilities from when the out-focus status starts to the particularpoint of time becomes equal to or greater than a preset threshold value,and may determine a period from when the out-focus status starts to thedetected particular point of time as the period in which the out-focusstatus is to be maintained.

FIG. 14 is a flowchart illustrating a method of determining reliabilityof a period in which an out-focus status is to be maintained based on anout-focus probability according to a context, the method being performedby a device, according to an embodiment of the present disclosure.

Referring to FIG. 14, in operation S1410, a device 100 may determinereliability of a period in which an out-focus status is to be maintainedbased on an out-focus probability of a period from when the out-focusstatus has started to when the out-focus status is to be maintained.

For example, the device 100 may determine the reliability of the periodin which the out-focus status is to be maintained based on an averagevalue of out-focus probabilities of the period from when the out-focusstatus has started to when the out-focus status is maintained.

In operation S1420, the device 100 may adjust the reliability of theperiod in which the out-focus status is to be maintained based on anout-focus probability corresponding to a location of the device 100.

The device 100 may determine the location of the device 100 when theout-focus status has started. The device 100 may obtain an out-focusprobability corresponding to the determined location based on theout-focus probability according to the location.

The device 100 may adjust the reliability of the period in which theout-focus status is to be maintained based on the out-focus probabilitycorresponding to the location.

In operation S1430, the device 100 may adjust the reliability of theperiod in which the out-focus status is to be maintained based on anout-focus probability corresponding to a status of the device 100.

The device 100 may determine the status of the device 100 when theout-focus status has started. The device 100 may obtain an out-focusprobability corresponding to the determined status based on theout-focus probability according to the status. The device 100 may adjustthe reliability of the period in which the out-focus status is to bemaintained based on the out-focus probability corresponding to thestatus.

Referring again to FIG. 14, the time, the location of the device 100,and the status of the device 100 are described as parameters to beconsidered so as to determine the reliability of the period in which theout-focus status is to be maintained. However, the device 100 mayconsider another context of the device 100 other than the parameters andmay determine the reliability of the period in which the out-focusstatus is to be maintained.

For example, according to status values of contexts of the device 100,the device 100 may determine a context among the contexts whosedifference between its status value and the out-focus probability isequal to or greater than a reference as a parameter to determine thereliability of the period in which the out-focus status is to bemaintained.

The device 100 may vary a weight of the contexts and may determine thereliability of the period in which the out-focus status is to bemaintained. For example, according to the status values of the contextsof the device 100, the greater a difference between a value of theout-focus probability and a status value of a context among the contextsis, the greater the weight added by the device 100 to the context.

In an embodiment, when an out-focus probability according to a contextof the device 100 when the out-focus status has started is within areference range, the device 100 may not consider, in calculating thereliability, the context whose out-focus probability is within thereference range. For example, the reference range may be between 45%through 55%.

For example, when an out-focus probability at a particular location isbetween 45% through 55%, a probability whether or not the user uses thedevice 100 at the particular location may be considered as meaninglessdata, thus, the device 100 may not consider the context whose out-focusprobability is within the reference range.

FIG. 15 illustrates a diagram related to a method of determining aperiod in which an out-focus status is to be maintained based onout-focus probabilities according to time, the method being performed bya device, according to an embodiment of the present disclosure.

Referring to FIG. 15, a device 100 may determine the period in which theout-focus status is to be maintained based on the out-focusprobabilities according to time.

For example, when a time when the out-focus status has started is 9:30a.m., the device 100 may obtain an out-focus probability correspondingto 9:30 a.m. based on the out-focus probabilities according to time.

When the out-focus probability corresponding to 9:30 a.m. is 90%, thedevice 100 may determine whether or not 90% is equal to or greater thana threshold value. If the threshold value is 75%, the device 100 maydetermine that the out-focus probability corresponding to 9:30 a.m. isequal to or greater than the threshold value.

When the device 100 determines that the out-focus probabilitycorresponding to 9:30 a.m. is equal to or greater than the thresholdvalue, the device 100 may detect a point of time when an out-focusprobability among out-focus probabilities of time periods after 9:30a.m. initially becomes less than the threshold value. Referring to FIG.15, the point of time when the out-focus probability among the out-focusprobabilities of the time periods after 9:30 a.m. initially becomes lessthan 75% is the threshold value of 11:50 a.m.

Since the point of time when the out-focus probability initially becomesless than the threshold value is detected, the device 100 may determinea time period of 2 hours and 20 minutes from 9:30 a.m. when theout-focus status has started, to 11:50 a.m. when the out-focusprobability initially becomes less than the threshold value, as theperiod in which the out-focus status is to be maintained.

The device 100 may determine, as reliability of the period of theout-focus status, an average value of out-focus probabilitiescorresponding to the period in which the out-focus status is to bemaintained. Referring to FIG. 15, the device 100 may determine 80%, thatis an average value of out-focus probabilities from 9:30 a.m. to 11:50a.m., as the reliability of the time period of 2 hours and 20 minutes.

When a threshold value of preset reliability is 70%, the device 100 maydetermine that the device 100 will have an out-focus status during thetime period of 2 hours and 20 minutes.

FIG. 16A illustrates a diagram related to a method of adjustingreliability by considering an out-focus probability at a location wherean out-focus status has started according to an embodiment of thepresent disclosure.

Referring to FIG. 16A, a device 100 may adjust the reliability byconsidering the out-focus probability at the location where theout-focus status has started.

The device 100 may determine that the location where the out-focusstatus has started is a movement path 1 based on latitude and longitudeinformation of the location where the out-focus status has started. Thedevice 100 may also determine that the location where the out-focusstatus has started is the movement path 1 based on an IP address of anaccess point that connects the device 100 to a network.

Based on the out-focus probability according to the location, the device100 may obtain an out-focus probability at the movement path 1. When theout-focus probability in a place 1 is 10%, the device 100 may determine30% as the reliability of the time period of 2 hours and 20 minutes byaveraging or weight-averaging 80% and 10%, wherein 80% is thereliability of the period in which the out-focus status is to bemaintained, which is determined with reference to FIG. 15, and 10% isthe out-focus probability in place 1.

If the reliability for which a location is further considered dropsbelow 30%, the device 100 may not determine that the out-focus statuswill be maintained during the time period of 2 hours and 20 minutes.

FIG. 16B illustrates a diagram related to a method of adjustingreliability by considering an out-focus probability corresponding to astatus of a device when an out-focus status has started according to anembodiment of the present disclosure.

Referring to FIG. 16B, a device 100 may adjust the reliability byconsidering an out-focus probability corresponding to a wearable deviceconnected to the device 100 when the out-focus status has started.

For example, the out-focus probability may be 30% when the wearabledevice is not connected to the device 100, the out-focus probability maybe 85% when a watch is connected to the device 100, and the out-focusprobability may be 90% when glasses are connected to the device 100.

When the device 100 determines that the out-focus status has started,the device 100 may obtain identification information of the wearabledevice connected to the device 100. The device 100 may also obtain anout-focus probability corresponding to the obtained identificationinformation of the wearable device.

In a case where the identification information of the wearable deviceconnected to the device 100 indicates the watch and the out-focusprobability corresponding to the watch is 85%, the device 100 maydetermine 70% as the reliability of the time period of 2 hours and 20minutes by averaging or weight-averaging 80%, 10%, and 85%, wherein 80%is the reliability of the period in which the out-focus status is to bemaintained, which is determined with reference to FIG. 15, 10% is theout-focus probability in place 1 shown in FIG. 16A, and 85% is theout-focus probability corresponding to the watch.

If the reliability for which the identification information of thewearable device is further considered increases up to 70%, the device100 may determine that the out-focus status will be maintained duringthe time period of 2 hours and 20 minutes.

FIG. 17A is a flowchart illustrating a method of re-determiningreliability of a period in which an out-focus status is to be maintainedsince a status value of a context of a device is changed, the methodbeing performed by a device, according to an embodiment of the presentdisclosure.

Referring to FIG. 17A, in operation S1710, a device 100 having theout-focus status may determine whether or not a location of the device100, a status of the device 100, or a surrounding environment of thedevice 100 is changed.

For example, the device 100 may determine whether earphones areconnected or disconnected, the location of the device 100 is changed andthus exceeds a reference range, or illuminance surrounding the device100 is changed and thus exceeds a reference range.

In operation S1720, when the device 100 determines that the status valueof the context of the device 100 has been changed, the device 100 mayre-determine, based on a changed status value, reliability of the periodin which the out-focus status is to be maintained.

For example, when the device 100 determines that the location of thedevice 100 is changed and thus exceeds the reference range, ordetermines that a wearable device that has been connected to the device100 is disconnected, the device 100 may re-determine the reliability ofthe period in which the out-focus status is to be maintained based on anout-focus probability at a changed location or an out-focus probabilitywhen the wearable device is not connected.

FIGS. 17B and 17C illustrate diagrams related to a method ofre-determining reliability of a period in which an out-focus status isto be maintained since a status value of a context of a device ischanged, the method being performed by a device, according to variousembodiments of the present disclosure.

Referring to FIG. 17B, when a device 100 determines that the out-focusstatus has started at 5:10 a.m., the device 100 may determine based oninformation about out-focus probabilities according to time, a timeperiod from 5:10 a.m. to 5:55 a.m. as the period in which the out-focusstatus is to be maintained.

In this case, the device 100 may calculate reliability of the period inwhich the out-focus status is to be maintained based on an out-focusprobability corresponding to the period in which the out-focus status isto be maintained, and based on a transportation type when the out-focusstatus has started.

For example, based on 75% that is an average value of out-focusprobabilities corresponding to the time period from 5:10 a.m. to 5:55a.m., and 90% that is an out-focus probability corresponding to a walkthat is the transportation type when the out-focus status has started,the device 100 may determine 80% as the reliability of the period inwhich the out-focus status is to be maintained.

When the reliability of the period in which the out-focus status is tobe maintained is equal to or greater than a threshold value, the device100 may stop an operation of an application that is executed in thedevice 100.

Referring to FIG. 17C, if the transportation type is changed from thewalk to the subway, the device 100 may re-determine, when thetransportation type is changed to the subway, the reliability of theperiod in which the out-focus status is to be maintained.

When a location of the device 100 is changed, the device 100 maydetermine a transportation type based on the location and a movementspeed of the device 100. When the transportation type is changed, thedevice 100 may re-determine based on an out-focus probabilitycorresponding to a changed transportation type, the reliability of theperiod in which the out-focus status is to be maintained.

For example, after the operation of the application is stopped and whilethe out-focus status is maintained, if the transportation type ischanged from the walk to the subway, the device 100 may change thereliability of the period in which the out-focus status is to bemaintained, to 30% based on 20% that is an out-focus probabilitycorresponding to the subway.

When the reliability of the period in which the out-focus status is tobe maintained is changed to 30%, the device 100 may resume the stoppedoperation of the application.

Therefore, when the location, the status, or the surrounding environmentof the device 100 is changed, the device 100 may improve efficiency ofpower consumption of a battery of the device 100 based on the changedinformation.

FIG. 18 is a flowchart illustrating a method of stopping an operation ofan application executed in a device based on a period in which anout-focus status is to be maintained and reliability of the period, themethod being performed by a device, according to an embodiment of thepresent disclosure.

Referring to FIG. 18, in operation S1810, when a device 100 does notreceive a user input from a user, the device 100 may determine whetheror not an out-focus status in which the user does not use the device 100has started. Operation S1810 may be described with reference to FIGS. 4Athrough 5.

In operation S1820, when the device 100 determines that the out-focusstatus has started, the device 100 may determine the period in which theout-focus status is to be maintained and the reliability of the periodbased on information about an out-focus probability according to acontext of the device 100. Operation S1820 may be described withreference to FIGS. 6 through 17C.

In operation S1830, when the period in which the out-focus status is tobe maintained and the reliability of the period are equal to or greaterthan a reference, the device 100 may stop the operation of theapplication executed in the device 100.

When the period in which the out-focus status is to be maintained isequal to or greater than a reference time period, the device 100 maystop the operation of the application executed in the device 100.

For example, when a background application that exchanges data with aserver is executed in the device 100 without the user input, the device100 may stop the data exchange between the background application andthe server.

In this case, if a plurality of background applications are executed inthe device 100, the device 100 may sequentially stop backgroundapplications which are less used among the plurality of backgroundapplications. If the period in which the out-focus status is to bemaintained is increased or the reliability of the period is increased,the number of background applications whose operations are stopped bythe device 100 may also be increased.

For example, in a case where event information indicating the occurrenceof the event is output if a preset event occurs, the device 100 may notoutput the event information even if the event occurs.

In this case, the device 100 may not output only event information of anevent that is from among a plurality of events and whose importance isequal to or less than a preset reference.

The device 100 may determine an event not to be output according to thereliability of the period in which the out-focus status is to bemaintained, and may not output only event information of the determinedevent. The event not to be output according to the reliability of theperiod in which the out-focus status is to be maintained may be presetin the device 100. For example, when the reliability of the period inwhich the out-focus status is to be maintained is set high, the device100 may not output an event with high importance.

For example, in a case where an application is updated without a userinput based on updated data received from a server, the device 100 maynot receive the updated data from the server. In this case, the device100 may not receive updated data for only an application whose number oftimes of use is equal to or less than a reference.

Based on information about an application use pattern of the user, thedevice 100 may adjust a position, a shape, a size, or a color of an iconof an application according to the context of the device 100, and thusmay allow the application which is frequently used according to thecontext of the device 100, to be more easily found than an applicationthat is not frequently used.

FIG. 19 illustrates a table related to a method of controlling anoperation of a background application, the method being performed by adevice having an out-focus status, according to an embodiment of thepresent disclosure.

Referring to FIG. 19, a device 100 may control data exchange of thebackground application based on a period in which an out-focus status isto be maintained.

The background application may indicate an application that continuouslyperforms a particular function in the device 100 but whose execution isnot recognizable by a user.

The background application may be one application or may be a modulethat forms one application. When the background application is themodule that forms one application, the background application may bereferred to as a background process or a background service.

For example, the background application may include, but is not limitedto, a module configured to periodically monitor particular data via anetwork, a module configured to periodically receive a rich site summary(RSS) feed from an external server via the network and to parse receivedextensible mark-up language (XML) data, a module in a social networkapplication configured to periodically exchange data with a server, amodule in a location tracking application configured to periodicallyreceive data from a GPS satellite, and a module in a motion recognitionapplication configured to periodically sense a motion of the user.

When the period in which the out-focus status is to be maintained, whichis calculated based on the out-focus status according to the context ofthe device 100, is equal to or greater than 30 minutes, the device 100may not limit the data exchange of the background application.

When the period in which the out-focus status is to be maintained isequal to or greater than 30 minutes, the device 100 may set as a mode 1,a data exchange control mode of the background application and may notreceive data of the background application for 5 minutes and may repeatan operation of receiving and transmitting data for the next 1 minute.

When the period in which the out-focus status is to be maintained isequal to or greater than 5 hours, the device 100 may set as a mode 2,the data exchange control mode of the background application and may notreceive data of the background application for 25 minutes and may repeatan operation of receiving and transmitting data for the next 5 minutes.

When the device 100 receives a user input during the period in which theout-focus status is supposed to be maintained, and thus the out-focusstatus is ended, the device 100 may resume the stopped data exchange.

Accordingly, as the period in which the out-focus status is to bemaintained is increased, the number of times the data exchange isperformed per hour is decreased, and thus the device 100 may improveefficiency of power consumption of a battery of the device 100.

FIG. 20 illustrates a table related to a method of stopping an operationof an application according to reliability of a period in which anout-focus status is to be maintained, the method being performed by adevice, according to an embodiment of the present disclosure.

Referring to FIG. 20, a device 100 may adjust a range of the applicationwhose operation is to be stopped according to the reliability of theperiod in which the out-focus status is to be maintained.

For example, when the reliability of the period in which the out-focusstatus is to be maintained is between 60% and 70%, the device 100 maystop data exchange or update of an application whose number of times ofexecution is between 0% and 20%. When the reliability of the period inwhich the out-focus status is to be maintained is between 70% and 80%,the device 100 may stop data exchange or update of an application whosenumber of times of execution is between 0% and 50%. When the reliabilityof the period in which the out-focus status is to be maintained isbetween 80% and 99%, the device 100 may stop data exchange or update ofan application whose number of times of execution is between 0% and 80%.

Accordingly, when the reliability of the period in which the out-focusstatus is to be maintained is increased, the number of applicationswhose operations are stopped by the device 100 is also increased, sothat the device 100 may improve efficiency of power consumption of abattery of the device 100.

In an embodiment, the device 100 may adjust, according to a state of abattery of the device 100, a range of an application for which dataexchange and update are to be limited. For example, when a remainingpower of the battery is high, the device 100 may stop data exchange orupdate of an application whose number of times of execution is within arange of 0 to 20%. When a remaining power of the battery is neither lownor high, the device 100 may stop data exchange or update of anapplication whose number of times of execution is within a range of 0 to50%. When a remaining power of the battery is low, the device 100 maystop data exchange or update of an application whose number of times ofexecution is within a range of 0 to 80%. When the battery of the device100 is being charged, the device 100 may not stop data exchange orupdate of an application.

Accordingly, the lower the remaining power of the battery of the device100, the more the hourly power consumption of the battery is reduced.For example, while a data exchange cycle of an e-mail is set short, if aremaining power of the battery is low, the device 100 may not receivee-mails. Then, when the remaining power of the battery becomes equal toor greater than a preset reference, the device 100 may receive e-mailsfrom a mail server.

FIG. 21 illustrates a graph related to a method of controlling dataexchange of an application based on out-focus probabilities according totime, the method being performed by a device, according to an embodimentof the present disclosure.

Referring to FIG. 21, a device 100 may resume a stopped operation of anapplication before an end of a period in which an out-focus status is tobe maintained.

For example, when the out-focus status starts, the device 100 maydetermine the period in which the out-focus status is to be maintainedand may stop data exchange of a background application during theperiod. After the data exchange of the background application isstopped, the device 100 may calculate a time of the end of the period inwhich the out-focus status is to be maintained. The device 100 mayresume the stopped operation of the application before the end of theperiod in which the out-focus status is to be maintained. For example,when the time of the end of the period in which the out-focus status isto be maintained is 5:50 p.m., the device 100 may resume the stoppedoperation of the application at 5:45 p.m.

In this case, before the end of the period in which the out-focus statusis to be maintained, the device 100 may consider another context such asa location of the device 100, a status of the device 100, or asurrounding environment of the device 100 and thus may determine whetheror not to resume the stopped operation of the application.

For example, when an out-focus probability corresponding to the locationof the device 100, an out-focus probability corresponding to the statusof the device 100, and an out-focus probability corresponding to thesurrounding environment of the device 100 are considered at 5:45 p.m.,if the out-focus probabilities are equal to or greater than a reference,the device 100 may not resume the stopped operation of the applicationand may stop the operation of the application until the device 100receives a user input or the location, the status, or the surroundingenvironment is changed.

Based on an application execution probability according to a context ofthe device 100, the device 100 may resume only an operation of aparticular application.

For example, after the end of the period in which the out-focus statusis to be maintained, if a probability that a game application is to beexecuted is equal to or greater than a reference, the device 100 mayresume only data exchange and updating with respect to the gameapplication.

For example, at 5 minutes before the end of the period in which theout-focus status is to be maintained, the device may obtain an executionprobability of an application corresponding to the location of thedevice 100. In a case where an execution probability of the gameapplication is highest at 5 minutes before the end of the period inwhich the out-focus status is to be maintained, the device 100 mayresume only the data exchange and the updating with respect to the gameapplication.

FIGS. 22A and 22B illustrate diagrams related to a method of controllingan event when the event occurs during an out-focus status, the methodbeing performed by a device, according to various embodiments of thepresent disclosure.

Referring to FIG. 22A, when the event occurs, if a period in which anout-focus status is to be maintained is equal to or greater than areference time period, or if a probability of the out-focus status isequal to or greater than a reference value, the device 100 may notdisplay information about the event on a screen.

For example, when the device 100 receives push data from a push server3000 in which identification information of the device 100 wasregistered, the device 100 may generate an event indicating reception ofthe push data. In this regard, when the event occurs, if the period inwhich the out-focus status is to be maintained is equal to or greaterthan the reference time period or if a probability of the out-focusstatus is equal to or greater than the reference value, the device 100may not display information about the generated event. The push data mayinclude, but is not limited to, a text message, an e-mail, or a chatmessage.

For example, when a user sets an alarm or a schedule in the device 100,the device 100 may generate an alarm event or a schedule event at a settime. In this regard, when the alarm event or the schedule event occurs,if the period in which the out-focus status is to be maintained is equalto or greater than the reference time period or if a probability of theout-focus status is equal to or greater than the reference value, thedevice 100 may not output information about the alarm event or theschedule event.

Referring to FIG. 22B, during the out-focus status shown in FIG. 22A, ifthe device 100 receives a user input for cancelling the out-focusstatus, the device 100 may output event information that was not output.

The user input for cancelling the out-focus status may correspond to aninput for touching a screen of the device 100 or pressing a presetbutton key of the device 100 in a lock status of the device 100.

When the user input for cancelling the out-focus status is received, thedevice 100 may output the event information by using an output methodthat was preset in correspondence to an event. For example, when amethod of outputting a text message is set in such a manner that contentof the text message is displayed on the screen and a vibration notice isoutput to indicate reception of the text message, the device 100 maydisplay content 2010 of a message on the screen and may generate avibration.

Accordingly, during the out-focus status when the period in which theout-focus status is to be maintained is equal to or greater than thereference time period or when the event occurs, if the probability ofthe out-focus status is equal to or greater than the reference value thedevice 100 may not output the event information and thus may increaseefficiency of power consumption of a battery of the device 100.

FIG. 23 illustrates a device in relation to a method of displayingidentification information of an application based on an executionprobability of the application according to a context of the device, themethod being performed by a device, according to an embodiment of thepresent disclosure.

Referring to FIG. 23, a device 100 may display a plurality of pieces ofidentification information of applications based on executionprobabilities of the applications according to the context in order toallow applications having higher execution probabilities to be moreeasily accessible.

The device 100 may allow the applications having higher executionprobabilities to be displayed upward or leftward on the screen, butembodiments are not limited thereto. For example, when executionprobabilities of a plurality of applications installed in the device 100are in descending order of a web browser 2310, a social networkingservice (SNS) application 2320, a game application 2330, a textapplication 2340, and a bank application 2350, the device 100 maydisplay icons on an edge screen, which is always accessible to a user,in an order of the web browser 2310, the SNS application 2320, the gameapplication 2330, the text application 2340, and the bank application2350.

The device 100 may also allow identification information of anapplication having a high execution probability to be displayed with ahigh brightness or a high chroma. The device 100 may also allow theidentification information of the application having a high executionprobability to be further displayed largely. The device 100 may alsoallow the identification information of the application having a highexecution probability to be displayed with an intuitional form, and mayallow identification information of an application having a lowexecution probability to be displayed with an unusual form.

When a status value of the context of the device 100 is changed, thedevice 100 may obtain execution probabilities of applicationscorresponding to a changed status value and may display the applicationsbased on the obtained execution probabilities of the applications sothat the higher the execution probabilities, the easier theaccessibility with respect to the applications.

For example, when a location of the device 100 is changed, the device100 may obtain execution probabilities of the applications at a changedlocation and may display the applications, based on the obtainedexecution probabilities of the applications, so that applications havinghigher execution probabilities have easier accessibility with respect toother applications.

FIGS. 24A and 24B illustrate a device in relation to a method ofproviding a user interface for controlling an operation of anapplication based on a use pattern of a user, the method being performedby a device, according to various embodiments of the present disclosure.

Referring to FIG. 24A, a device 100 may provide a menu for controllingthe operation of the application based on the use pattern of the user.

When the device 100 receives a user input for selecting the menu forcontrolling the operation of the application based on the use pattern ofthe user, the device 100 may display a check-box button 2410 to selectwhether to execute a function for controlling the operation of theapplication based on the use pattern of the user.

Referring to FIG. 24B, when the device 100 receives a user input forselecting the check-box button 2410 shown in FIG. 24A, the device 100may display a selection window 2420 including a description indicatingthat the operation of the application may be limited.

When the device 100 receives a user input for selecting a confirm buttonon the selection window 2420, the device 100 may stop the operation ofthe application based on the use pattern of the user, and thus mayincrease efficiency of power consumption of a battery of the device 100.

FIG. 25 illustrates a block diagram of a device according to anembodiment of the present disclosure.

Referring to FIG. 25, a device 100 may include a user input unit 145, acommunicator 130, a display unit 110, and a controller 170. However, notall elements shown in FIG. 25 are necessary elements. That is, thedevice 100 may be embodied with more or less elements than the elementsshown in FIG. 25.

The user input unit 145 may receive an input from a user.

The user input unit 145 may receive a user input from the user after anoperation of an application is stopped during an out-focus status.

The communicator 130 may exchange data with a peripheral device or aserver.

The communicator 130 may exchange data of a background application withthe server. Accordingly, even if a user input is not received, thecommunicator 130 may exchange data with respect to an application withthe server.

The communicator 130 may receive updated data with respect to theapplication from the server. Therefore, even if a user input is notreceived, the communicator 130 may receive the updated data with respectto the application from the server.

The communicator 130 may receive a call connection request from atelephone network server.

The display unit 110 may display information.

When the call connection request is received, the display unit 110 mayoutput information indicating reception of the call connection request.

The controller 170 may control a configuration of the device 100including the user input unit 145, the communicator 130, and the displayunit 110.

When a user input is not received, the controller 170 may determinewhether an out-focus status in which the user does not use the device100 has started.

For example, when the user input is not received during at least apreset time period, the controller 170 may inactivate the display unit110. When the display unit 110 is inactivated, the controller 170 maydetermine that the out-focus status has started.

For example, when a user input for confirming the call connectionrequest in response to output event information is not received, thecontroller 170 may determine that the out-focus status has started.

When the controller 170 determines that the out-focus status hasstarted, the controller 170 may determine a period in which theout-focus status is to be maintained based on a probability of theout-focus status according to a context of the device 100.

For example, the controller 170 may determine the period in which theout-focus status is to be maintained based on a value of a probabilityof the out-focus status corresponding to a time period after theout-focus status has started, wherein the value of the probability isfrom among information about out-focus probabilities according to time.

When the determined period in which the out-focus status is to bemaintained is equal to or greater than a reference time period, thecontroller 170 may stop an operation of an application executed in thedevice 100.

The controller 170 may determine reliability of the period in which theout-focus status is to be maintained based on information about a deviceuse pattern of the user and when the reliability of the period in whichthe out-focus status is to be maintained is equal to or greater than areference, the controller 170 may stop the operation of the applicationexecuted in the device 100.

For example, the controller 170 may determine the reliability of theperiod in which the out-focus status is to be maintained based on aprobability value corresponding to a location of the device 100 when theout-focus status has started, wherein the probability value is fromamong information about probabilities of the out-focus status accordingto locations of the device 100.

As another example, the controller 170 may determine the reliability ofthe period in which the out-focus status is to be maintained based on aprobability value corresponding to a status of the device 100 when theout-focus status has started, wherein the probability value is fromamong information about probabilities of the out-focus status accordingto statuses of the device 100.

When the period in which the out-focus status is to be maintained isequal to or greater than the reference time period, the controller 170may control the communicator 130 to stop data exchange of the backgroundapplication.

When the period in which the out-focus status is to be maintained isequal to or greater than the reference time period, the controller 170may control the communicator 130 not to receive updated data withrespect to the application from the server.

When the period in which the out-focus status is to be maintained isequal to or greater than the reference time period, even if informationabout an event is received from the server, the controller 170 may notrequest the display unit 110 to output information indicating receptionof the event.

When a user input is received from the user, the controller 170 mayresume the stopped operation of the application.

The device 100 may include an output unit. The output unit may outputinformation to a user. For example, the output unit may include thedisplay unit 110 or a speaker 160 shown in FIG. 26.

A configuration of a device 100 may be applied to various types ofdevices such as a mobile phone, a tablet PC, a personal digitalassistant (PDA), a Moving Picture Experts Group phase 1 or phase 2(MPEG-1 or MPEG-2) audio layer 3 (MP3) player, a kiosk, an electronicphotoframe, a navigation device, a digital television (TV), a smartwatch, a wristwatch, or a wearable device such as smart glasses,head-mounted display (HMD), or the like.

Referring again to FIG. 26, a device 100 may include the communicator130, the user input unit 145, the display unit 110, and the controller170, and may further include at least one of a memory 120, a GPS chip125, a video processor 135, an audio processor 140, a microphone 150, animage-capturing unit 155, a speaker 160, a motion detector 165, and thebattery 180.

The display unit 110 may include a display panel 111 and a controller(not shown) that controls the display panel 111. The display panel 111may be embodied as various displays including a liquid crystal display(LCD) display, an organic light-emitting diode (OLED) display, an activematrix OLED (AMOLED) display, a plasma display panel (PDP), or the like.The display panel 111 may be formed to be flexible, transparent, impactresistant, and/or wearable. The display panel 111 may be combined with atouch panel 147 of the user input unit 145, and thus may be provided asa touchscreen (not shown). For example, the touchscreen may include anintegrated module having a stack structure containing the display panel111 and the touch panel 147.

The memory 120 may include at least one of an internal memory (notshown) and an external memory (not shown).

The internal memory may include at least one of a volatile memory (e.g.,a dynamic RAM (DRAM), a static RAM (SRAM), a synchronous DRAM (SDRAM),etc.), a non-volatile memory (e.g., a one-time programmable read-onlymemory (OTPROM), a PROM, an erasable and programmable ROM (EPROM), anelectrically erasable and programmable ROM (EEPROM), a mask ROM, a flashROM, etc.), a hard disk drive (HDD), and a solid-state drive (SSD).According to an embodiment, the controller 170 may load a command ordata, which is received from at least one of the non-volatile memory andanother element, to the volatile memory, and may process the command orthe data. Also, the controller 170 may store, in the non-volatilememory, data that is received from or is generated by another element.

The external memory may include at least one of a compact flash (CF)memory, a secure digital (SD) memory, a micro-SD memory, a mini-SDmemory, an extreme digital (xD) memory, and a memory stick.

The memory 120 may store various programs and data used in operations ofthe device 100. For example, the memory 120 may temporarily orsemi-permanently store a portion of contents to be displayed on a lockscreen.

The controller 170 may control the display unit 110 to display a portionof contents which is stored in the memory 120. That is, the controller170 may display, on the display unit 110, the portion of the contentswhich is stored in the memory 120. Alternatively, when a user's gestureis performed in a region of the display unit 110, the controller 170 mayperform a control operation that corresponds to the user's gesture.

The controller 170 may include at least one of a RAM 171, a ROM 172, acentral processing unit (CPU) 173, a graphics processing unit (GPU) 174,and a bus 175. The RAM 171, the ROM 172, the CPU 173, and the GPU 174may be connected to each other via the bus 175.

The CPU 173 accesses the memory 120, and performs a booting operation byusing an operating system (O/S) stored in the memory 120. Also, the CPU173 performs various operations by using the various programs, aplurality of items of content, a plurality of items of data, etc. whichare stored in the memory 120.

The ROM 172 stores a command set for booting up a system. For example,when a turn-on command is input to the device 100, and power is suppliedto the device 100, the CPU 173 may copy the operating system stored inthe memory 120 to the RAM 171, according to the command stored in theROM 172, may execute the operating system, and thus may boot up thesystem. When the booting operation is completed, the CPU 173 copies thevarious programs stored in the memory 120 to the RAM 171, and performsthe various operations by executing the programs copied to the RAM 171.When the device 100 is booted up, the GPU 174 displays a user interfacescreen in a region of the display unit 110. In more detail, the GPU 174may generate a screen that displays an electronic document includingvarious objects such as content, an icon, a menu, or the like. The GPU174 calculates coordinate values of the objects that are to be displayedaccording to a layout of the user interface screen, and calculatesattribute values of shapes, sizes, or colors of the objects. Then, theGPU 174 may generate user interface screens with various layoutsincluding the objects based on the calculated attribute values. The userinterface screen generated by the GPU 174 may be provided to the displayunit 110 and thus may be displayed in areas of the display unit 110.

The GPS chip 125 may receive a GPS signal from a GPS satellite and maycalculate a current position of the device 100. In a case where anavigation program is used or a current position of the user isrequired, the controller 170 may calculate a position of the user byusing the GPS chip 125.

The communicator 130 may communicate with various external devicesaccording to various types of communication methods. The communicator130 may include at least one of a Wi-Fi chip 131, a Bluetooth chip 132,a wireless communication chip 133, and a near field communication (NFC)chip 134. The controller 170 may communicate with the various externaldevices by using the communicator 130.

The Wi-Fi chip 131 and the Bluetooth chip 132 may perform communicationby using Wi-Fi and Bluetooth, respectively. If the Wi-Fi chip 131 or theBluetooth chip 132 is used, the Wi-Fi chip 131 or the Bluetooth chip 132may first transmit and receive various types of connection informationincluding a service set identification (SSID), a session key, or thelike, may establish a connection for communication by using theconnection information, and then may transmit and receive various typesof information. The wireless communication chip 133 may indicate a chipthat performs communication according to various communication standardssuch as the Institute of Electrical and Electronics Engineers (IEEE),ZigBee, 3^(rd) generation (3G), 3G Partnership Project (3GPP), long termevolution (LTE), or the like. The NFC chip 134 indicates a chip thatoperates using NFC by using a 13.56 MHz band from among various radiofrequency-identification (RF-ID) frequency bands such as 135 kHz, 13.56MHz, 433 MHz, 860 through 960 MHz, 2.45 GHz, or the like.

The video processor 135 may process video data included in contentreceived by using the communicator 130 or may process video dataincluded in content stored in the memory 120. The video processor 135may perform various image processing such as decoding, scaling, noisefiltering, frame rate conversion, resolution conversion, or the like onthe video data.

The audio processor 140 may process audio data included in contentreceived by using the communicator 130 or may process audio dataincluded in content stored in the memory 120. The audio processor 140may perform various processing such as decoding, amplification, noisefiltering, or the like on the audio data.

When a reproducing program for multimedia content is executed, thecontroller 170 may reproduce the multimedia content by driving the videoprocessor 135 and the audio processor 140. The speaker 160 may outputaudio data generated in the audio processor 140.

The user input unit 145 may receive an input of various instructionsfrom a user. The user input unit 145 may include at least one of a key146, the touch panel 147, and a pen recognizing panel 148.

The key 146 may be of various types such as a mechanical button, awheel, or the like that may be formed in a front portion, a sideportion, a rear portion, etc., of an external surface of a body of thedevice 100.

The touch panel 147 may sense a touch input by the user and may output avalue of a touch event that corresponds to a signal generated by thesensed touch input. When the touch panel 147 is combined with thedisplay panel 111 and thus is formed as a touchscreen, the touchscreenmay be configured as a capacitive touchscreen, a resistive touchscreen,or a piezoelectric touchscreen by using various types of touch sensors.The capacitive touchscreen may calculate touch coordinates by sensing asmall amount of electricity generated when a body part of the usertouches the surface of the capacitive touchscreen, which is coated witha dielectric material. The resistive touchscreen may include twoembedded electrode plates and may calculate touch coordinates by sensinga flow of current that occurs when the user touches the resistivetouchscreen which causes upper and lower plates of a touched point tocontact each other. The touch event that occurs on the touchscreen maybe mainly generated by a finger of a person but may also be generated byan object formed of a conductive material capable of changingcapacitance.

The pen recognizing panel 148 may sense a proximity input or a touchinput of a touch pen (e.g., a stylus pen or a digitizer pen) which isperformed by a user, and may output a sensed pen proximity event or asensed pen touch event. The pen recognizing panel 148 may be anelectromagnetic resonance (EMR)-type pen recognizing panel, and maysense the touch input or the proximity input according to changes in astrength of an electromagnetic field, which occur when the touch penapproaches or touches the touchscreen. In more detail, the penrecognizing panel 148 may include an electromagnetic induction coilsensor (not shown) having a grid structure, and an electric signalprocessor (not shown) for sequentially providing an alternating current(AC) signal having a predetermined frequency to each loop coil of theelectromagnetic induction coil sensor. When a pen having an internalresonance circuit is positioned near a loop coil of the pen recognizingpanel 148, a magnetic field transmitted from the loop coil generates acurrent in the resonance circuit in the pen, based on mutualelectrostatic induction. Due to the current, an induction field isgenerated from a coil forming the resonance circuit in the pen, and thepen recognizing panel 148 detects the induction field from the loop coilcapable of receiving a signal, and thus senses the touch input or theproximity input by the pen. The pen recognizing panel 148 may bearranged to occupy a preset area below the display panel 111, e.g., mayhave a size capable of covering a display region of the display panel111.

The microphone 150 may receive an input of a user's voice or other soundand may convert the user's voice or other sound to audio data. Thecontroller 170 may use the user's voice, which is input via themicrophone 150, in a call-related operation or may convert the user'svoice to the audio data and may store the audio data in the memory 120.

The image-capturing unit 155 may capture a still image or a movingpicture according to a control by the user. The image-capturing unit 155may be plural in number and include a front camera, a rear camera, orcombinations thereof.

If the image-capturing unit 155 and the microphone 150 are formedtogether, the controller 170 may perform a control operation accordingto a user's voice input via the microphone 150 or a user's motionrecognized by the image-capturing unit 155. For example, the device 100may operate in a motion control mode or a voice control mode. If thedevice 100 operates in the motion control mode, the controller 170 mayactivate the image-capturing unit 155 and may capture an image of theuser, may trace a change in motions of the user, and may perform acontrol operation corresponding thereto. If the device 100 operates inthe voice control mode (i.e., a voice recognition mode), the controller170 may analyze a user's voice input via the microphone 150, and mayperform a control operation according to the analyzed user's voice.

The motion detector 165 may detect movement of a body of the device 100.The device 100 may rotate or may tilt in various directions. Here, themotion detector 165 may detect a movement characteristic such as arotation direction, a rotation angle, a tilted angle, or the like byusing at least one of various sensors including a magnetic sensor, agyroscope sensor, an acceleration sensor, etc.

Although not illustrated in FIG. 26, the present embodiment may furtherinclude a universal serial bus (USB) port for connecting the device 100and a USB connector, various external input ports including a headset, amouse, a local area network (LAN), etc. for connection with variousexternal terminals, a digital multimedia broadcasting (DMB) chip forreceiving and processing a DMB signal, various sensors, or the like.

Names of the elements of the device 100 may be changed. Also, the device100 according to the present embodiment may be embodied by including atleast one of the elements, or may be embodied with more or less elementsthan the elements.

The various embodiments may be embodied as computer readablecode/instructions on a recording medium, e.g., a program module to beexecuted in computers, which include computer-readable commands. Thecomputer storage medium may include any usable medium that may beaccessed by computers, volatile and non-volatile medium, and detachableand non-detachable medium. Also, the computer storage medium may includea computer storage medium and a communication medium. The computerstorage medium includes all volatile and non-volatile media, anddetachable and non-detachable media which are technically implemented tostore information including computer readable commands, data structures,program modules or other data. The communication medium includescomputer-readable commands, a data structure, a program module, otherdata as modulation-type data signals such as carrier signals, or othertransmission mechanism, and includes other information transmissionmediums.

It should be understood that the various embodiments described hereinshould be considered in a descriptive sense only and not for purposes oflimitation. Descriptions of features or aspects within each embodimentshould typically be considered as available for other similar featuresor aspects in other embodiments. For example, configuring elements thatare singular forms may be executed in a distributed fashion, and also,configuring elements that are distributed may be combined and thenexecuted.

While the present disclosure has been shown and described with referenceto various embodiments thereof, it will be understood by those skilledin the art that various changes in form and detail may be made thereinwithout departing from the spirit and scope of the present disclosure asdefined by the appended claims and their equivalents.

What is claimed is:
 1. A device comprising: a touch screen; and at leastone processor configured to at least: when a user input is not receivedfor a preset time period via the touch screen, turn off the touch screenand determine that an out-focus status in which the user does not usethe device has started, based on both the out-focus status being startedand a current context of the device, identify a probability of theout-focus status being maintained, based on the identified probabilityof the out-focus status being maintained, calculate an expected periodin which the out-focus status is to be maintained from when theout-focus status has started, and based on both the out-focus statusbeing started and the expected period being equal to or greater than areference time period, stop an operation of an application which isbeing executed in a background on the device.
 2. The device of claim 1,wherein the out-focus status in which the user does not use the deviceindicates at least one of a status in which the touch screen does notoutput the information or a status in which the user does not receivethe information output from the touch screen.
 3. The device of claim 1,wherein the context of the device comprises at least one of a time, alocation of the device, a status of the device, or an environmentsurrounding the location of the device.
 4. The device of claim 1,wherein, after the application is stopped, the at least one processor isfurther configured to receive the user input via the touch screen fromthe user, and wherein, when the user input is received from the user,the at least one processor is further configured to resume the stoppedapplication.
 5. The device of claim 1, further comprising: a transceiverconfigured to receive a call connection request from a server, wherein,when the call connection request is received, the at least one processoris further configured to control the touch screen to output informationindicating reception of the call connection request, and wherein, when auser input for confirming the call connection request in response to theoutput information is not received, the at least one processor isfurther configured to determine that the out-focus status has started.6. The device of claim 5, wherein the at least one processor is furtherconfigured to: determine the expected period in which the out-focusstatus is to be maintained, based on a value of a probability of theout-focus status corresponding to a time period after the out-focusstatus has started, wherein the value of the probability is obtainedfrom among information about probabilities of the out-focus statusaccording to time.
 7. The device of claim 1, wherein the at least oneprocessor is further configured to determine reliability of the expectedperiod in which the out-focus status is to be maintained based oninformation about the probability of the out-focus status according tothe context of the device, and wherein, when the reliability of theexpected period in which the out-focus status is to be maintained isequal to or greater than a reference, the at least one processor isfurther configured to stop the application executed in the background onthe device.
 8. The device of claim 7, wherein the information about theprobability of the out-focus status according to the context of thedevice comprises information about probabilities of the out-focus statusaccording to locations of the device, wherein the at least one processoris further configured to determine the reliability of the expectedperiod in which the out-focus status is to be maintained based on aprobability value corresponding to a location of the device when theout-focus status has started, and wherein the probability value isobtained from among the information about the probabilities of theout-focus status according to the locations of the device.
 9. The deviceof claim 7, wherein the information about the probability of theout-focus status according to the context of the device comprisesinformation about probabilities of the out-focus status according tostatuses of the device, wherein the at least one processor is furtherconfigured to determine the reliability of the expected period in whichthe out-focus status is to be maintained based on a probability valuecorresponding to a status of the device when the out-focus status hasstarted, and wherein the probability value is obtained from among theinformation about the probabilities of the out-focus status according tothe statuses of the device.
 10. The device of claim 1, furthercomprising: a transceiver configured to exchange data about theapplication with the server, even if the user input is not received,wherein, when the expected period in which the out-focus status is to bemaintained is equal to or greater than the reference time period, the atleast one processor is further configured to control the transceiver tostop exchanging the data.
 11. The device of claim 10, wherein, even ifinformation about an event is received from a server, the at least oneprocessor is further configured not to request the transceiver to outputinformation indicating reception of the event when the expected periodin which the out-focus status is to be maintained is equal to or greaterthan the reference time period.
 12. The device of claim 1, furthercomprising: a transceiver configured to receive updated data withrespect to the application from a server even if the user input is notreceived, wherein, when the expected period in which the out-focusstatus is to be maintained is equal to or greater than the referencetime period, the at least one processor is further configured to controlthe transceiver not to receive the updated data from the server.
 13. Amethod of managing power comprising: when a user input is not receivedfrom a user for a preset time period via a touch screen, turning off thetouch screen and determining that an out-focus status in which the userdoes not use the device has started; based on both the out-focus statusbeing started and a current context of the device, identifying aprobability of the out-focus status being maintained, based on theidentified probability of the out-focus status being maintained,calculating an expected period in which the out-focus status is to bemaintained from when the out-focus status has started; and based on boththe out-focus status being started and the expected period being equalto or greater than a reference time period, stopping an operation of anapplication which is being executed in a background on the device. 14.The method of claim 13, wherein the out-focus status in which the userdoes not use the device, indicates at least one of a status in which thetouch screen of the device does not output information or a status inwhich the user does not receive the information output from the touchscreen of the device.
 15. The method of claim 13, wherein the context ofthe device comprises at least one of a time, a location of the device, astatus of the device, or an environment surrounding the location of thedevice.
 16. The method of claim 13, further comprising: after theapplication is stopped, receiving the user input via the touch screenfrom the user; and when the user input is received from the user,resuming the stopped application.
 17. The method of claim 13, furthercomprising: when a call connection request is received from a server,outputting information indicating reception of the call connectionrequest, wherein, when a user input for confirming the call connectionrequest in response to the output information is not received, thedetermining of the out-focus status comprises determining that theout-focus status has started.
 18. A non-transitory computer-readablerecording medium having recorded thereon one or more computer programsincluding instructions that, when executed by at least one processor,cause the at least one processor to control for executing the methodaccording to claim 13.